@prigiattiperrut cc. @forstisabella, this is a bit tricky:

This doesn't apply to just one scenario (opt-out), this applies to all scenario where there should be at least one enabled destination connected to a source. But then this gets complicated with combinations of unmapped destinations and other consent categories.

Let's think about how to do this.

just remembered we are going to be adding another table to this doc when engg finishes one other defect in the wrapper.

The new table can be seen here: https://docs.google.com/document/d/1o8XQ-9N6nBxR2XjNIrTPs6y6gZRnzU_38r3CNfo2esw/edit?tab=t.0#bookmark=id.lqel9qezsfmm and covers

@atitsh @prigiattiperrut

just remembered we are going to be adding another table to this doc when engg finishes one other defect in the wrapper.

The new table can be seen here: https://docs.google.com/document/d/1o8XQ-9N6nBxR2XjNIrTPs6y6gZRnzU_38r3CNfo2esw/edit?tab=t.0#bookmark=id.lqel9qezsfmm and covers

Are we still holding off on this one, or can we merge it now?

@forstisabella can you review this table and see how we could incorporate it in our onetrust wrapper doc now that the code fix has been deployed.

@forstisabella can you review this table and see how we could incorporate it in our onetrust wrapper doc now that the code fix has been deployed.

@atitsh - I sure can! In the meantime, should we close this PR or merge it?

close (not merge), we can leave it open as a reminder.